feat: more approachable & in-depth indexer intro#2055
Merged
ElliotFriend merged 1 commit intostellar:mainfrom Dec 19, 2025
Merged
feat: more approachable & in-depth indexer intro#2055ElliotFriend merged 1 commit intostellar:mainfrom
ElliotFriend merged 1 commit intostellar:mainfrom
Conversation
chadoh
force-pushed
the
feat/better-indexers-overview
branch
2 times, most recently
from
35941a1 to
272a74f
Compare
chadoh
force-pushed
the
feat/better-indexers-overview
branch
4 times, most recently
from
0205b40 to
bdc9e38
Compare
chadoh
commented
Dec 12, 2025
chadoh
force-pushed
the
feat/better-indexers-overview
branch
2 times, most recently
from
80dcc07 to
15358ee
Compare
chadoh
added a commit
to theahaco/stellar-docs
that referenced
this pull request
Dec 19, 2025
"deprecated", to my engineering-trained mind, means "there is a better alternative available that you should now switch to." There is ***no*** viable alternative to Horizon today. We therefore cannot declare it to be deprecated. When I read that it is _already_ deprecated, it makes me think I can avoid using it in a project. If I cannot realistically avoid using it, at least not without great cost in both engineering research time and infrastructure bills, then the assertion that it is already deprecated will cause me distress. Once we have good Portfolio API-style indexing services in place, with freemium models appropriate for the whole gamut of hackathon-startups-to-enterprises, then we can consider Horizon to be deprecated. Until then, there's just no other reasonable way to get a whole host of necessary data, such as token balances and circulating supply. This updates the "Horizon is deprecated" warning to say that it _will_ be deprecated in the future, deep-linking to the "Portfolio APIs" section of the [newly-revamped indexers page][1]. [1]: stellar#2055
chadoh
force-pushed
the
feat/better-indexers-overview
branch
from
15358ee to
c000e8f
Compare
chadoh
force-pushed
the
feat/better-indexers-overview
branch
2 times, most recently
from
b4bec0f to
e1f8a1b
Compare
Contributor
ElliotFriend
left a comment
ElliotFriend
left a comment
There was a problem hiding this comment.
some minor nits here and there, and some questions left throughout.
the headline, though: This looks like a great change!!! thank you so much!!
i18n/es/docusaurus-plugin-content-docs/current/data/indexers/README.mdx
Outdated
Show resolved
Hide resolved
Clean up the Data section's sidebar and add MUCH more info & context to the "Data -> Indexers" page. While mostly adding info, this removes the small Goldsky tutorial+screenshots that had been on this page. I'm not sure our documentation is the right place to walk through a partner's solution in this way. We already link out to Goldsky's documentation, which is quite good, containing more & better screenshots than what we had. Additionally, this sort of tutorial-via-screenshots content did not fit as well within the reworked Indexers homepage, which is a bit higher-level. I wasn't sure it was worth keeping this content anywhere, and decided to remove it for now. Co-authored-by: Elliot Voris <elliot@voris.me>
chadoh
force-pushed
the
feat/better-indexers-overview
branch
from
1ded476 to
66392a3
Compare
chadoh
added a commit
to theahaco/stellar-docs
that referenced
this pull request
Dec 20, 2025
"deprecated", to my engineering-trained mind, means "there is a better alternative available that you should now switch to." There is ***no*** viable alternative to Horizon today. We therefore cannot declare it to be deprecated. When I read that it is _already_ deprecated, it makes me think I can avoid using it in a project. If I cannot realistically avoid using it, at least not without great cost in both engineering research time and infrastructure bills, then the assertion that it is already deprecated will cause me distress. Once we have good Portfolio API-style indexing services in place, with freemium models appropriate for the whole gamut of hackathon-startups-to-enterprises, then we can consider Horizon to be deprecated. Until then, there's just no other reasonable way to get a whole host of necessary data, such as token balances and circulating supply. This updates the "Horizon is deprecated" warning to say that it _will_ be deprecated in the future, deep-linking to the "Portfolio APIs" section of the [newly-revamped indexers page][1]. [1]: stellar#2055
This was referenced Dec 23, 2025
briwylde08
pushed a commit
that referenced
this pull request
Jan 5, 2026
"deprecated", to my engineering-trained mind, means "there is a better alternative available that you should now switch to." There is ***no*** viable alternative to Horizon today. We therefore cannot declare it to be deprecated. When I read that it is _already_ deprecated, it makes me think I can avoid using it in a project. If I cannot realistically avoid using it, at least not without great cost in both engineering research time and infrastructure bills, then the assertion that it is already deprecated will cause me distress. Once we have good Portfolio API-style indexing services in place, with freemium models appropriate for the whole gamut of hackathon-startups-to-enterprises, then we can consider Horizon to be deprecated. Until then, there's just no other reasonable way to get a whole host of necessary data, such as token balances and circulating supply. This updates the "Horizon is deprecated" warning to say that it _will_ be deprecated in the future, deep-linking to the "Portfolio APIs" section of the [newly-revamped indexers page][1]. [1]: #2055
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Clean up the Data section's sidebar and add MUCH more info & context to the "Data -> Indexers" page.
While mostly adding info, this removes the small Goldsky tutorial+screenshots that had been on this page. I'm not sure our documentation is the right place to walk through a partner's solution in this way. We already link out to Goldsky's documentation, which is quite good, containing more & better screenshots than what we had. Additionally, this sort of tutorial-via-screenshots content did not fit as well within the reworked Indexers homepage, which is a bit higher-level. I wasn't sure it was worth keeping this content anywhere, and decided to remove it for now.